Problem
Email outputs from iMIS are not being sent. These emails could be merge process outputs, notifications to users (for example, when they register for an event through the Public view), or website error messages that are sent to the designated webmaster for your iMIS-based web content. Additionally, Outlook event invitations are not being sent to users who request them through the Public view of iMIS. (This might occur even if email outputs are working correctly.)
Solution
This problem can occur due to several causes:
■ Your organization's SMTP server was not specified correctly during installation of iMIS.
■ The domain name of your organization's SMTP server has changed since you installed iMIS.
■ Your organization's enterprise virus protection might have persistent port blocking rules (against mass-mailing worms) that were triggered if iMIS tried to send email notifications to you from an IP address that did not correspond to a trusted IP address.
Isolating the cause of the problem depends on which type of notification is not working correctly:
■ Outlook event invitations are handled by your Exchange webmail proxy server.
■ All other email outputs are handled by the SMTP server that is configured for each iMIS-related ASP.NET application.
Use the following steps to correct this problem:
To specify your global email settings
Some email-related settings are global to your entire organization regardless of how many application servers you have.
1. Specify the email address of the designated webmaster for your iMIS-based web content.
□ From iMIS System Setup, select Set up web component > Quick setup.
The Quick setup window appears.
□ In The default email address for the site field, enter the email address of the designated webmaster for your iMIS-based content.
2. (Event invitations only) Specify the Microsoft Exchange account information of the designated webmaster for your iMIS-based web content.
□ From iMIS System Setup, select Set up web component > Exchange settings.
The Exchange settings window appears.
□ In the Username field, specify your designated webmaster's domain user name required to log onto the proxy server for Exchange. For example, username. You may need to prefix the username with the domain name depending on the network location of the exchange server, such as domainname\username.
□ In the Password field, specify the corresponding domain password of your designated webmaster.
□ In the Exchange URL field, specify the namespace URL of your designated webmaster's Exchange user base mailbox folder (when connecting to your proxy server for Exchange). For example, https://webmail.myorg.org/exchange/userName/ if the Exchange server is configured for Outlook Web Access or exchangeserver.localdomain.local when the Exchange server is on a local network with your iMIS appserver.
Tip: You can test these three settings by opening an Internet Explorer browser and entering the Exchange URL that you've specified in this Exchange Settings window. You should get a domain authentication dialog asking for your user name and password. Enter the Username and Password that you've specified. If your web mail inbox appears, these settings are correct.
To specify your appserver-specific email settings
Some email-related settings are specific to each appserver, and even individually to each application on a server.
1. Modify the web.config files for all instances of your iMIS and iMISpublic applications to specify the domain name of the SMTP server to use for each.
□ On each appserver host, open the web.config files for each iMIS application.
■ iMIS default location: C:\Program Files\ASI\iMIS\net
■ iMISpublic default location: C:\Program Files\ASI\iMIS\iMIS_public
□ In each web.config file, search for the <network> element declaration and modify the value of the host attribute to specify the domain name of your organization's SMTP server. For example <network host="mysmtpsrv.myorg.org"…
Note: In the <network> element declaration, you can also specify port and authentication information for your SMTP server to ensure that iMIS can find and log onto to the SMTP server in your environment. For details, refer to your Microsoft ASP.NET documentation.
2. Restart each appserver on which you modified the web.config file.
3. Ask your network administrator to check your enterprise virus protection's port blocking rules to ensure that port 25 of the IP address corresponding to each iMIS appserver is not blocked.